Update ip-warm-up-overview.md - Added How many IP's do I need section #641
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
✔️ Deploy Preview for support-docs ready! 🔨 Explore the source changes: 35b80df 🔍 Inspect the deploy log: https://app.netlify.com/sites/support-docs/deploys/61c353b20f8e080008796ecd 😎 Browse the preview: https://deploy-preview-641--support-docs.netlify.app |
bkemper
reviewed
Dec 22, 2021
| * Other message stream examples: transactional, marketing, individual brands, regions, etc. | ||
| 2. What is the maximum volume that I need to send in a single day for each message stream? | ||
| * A single IP address can technically send a large volume of mail quickly depending on sending reputation - that’s millions of messages per hour. For most senders the recommended volume after a proper warmup is 2 to 5 million per day from a single IP. | ||
| * Senders with volume less than 500k messages per month or with inconsistent volume from week to week may not have enough volume to build and maintain a positive sending reputation with mailbox providers. In this case, a shared IP pool may result in better delivery and deliverability. |
There was a problem hiding this comment.
@tcrawford-SP It looks like the formatting is a little off causing it to have two "1."s. I'll fix that.
There was a problem hiding this comment.
I wonder why that happened.
bkemper
approved these changes
Dec 22, 2021
approved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
// Give your PR a recognizable title. For example: "FE-123: Add new prop to component" or "Resolve Issue #123: Fix bug in component" // Your PR title will be visible in changelogs
What Changed
// What changes does this PR propose? // Provide screenshots or screen recordings for any visual changes.
How To Test or Verify
// Describe any steps that may help reviewers verify changes. // Anything beyond basic unit testing, such as assistive tech usage, or special interactions.
PR Checklist
Below are some checklists to follow for the correct procedure in different circumstance. The first list ("All PRs Checklist") should be followed for ALL PRs. The next 2 are additive to this list depending on what type of PR you are using.
For example: If you are submitting a content change to one of the support documents, your checklist would include the:
If you are submitting a feature addition, enhancement, or bug fix, your checklist would include the:
All PRs Checklist
Content Changes Checklist
examples/article.mdin the root of the project directory and on the momentum doc's preface articleDevelopment Changes Checklist (some checks are automatic github actions and will not be listed here. ie. "all tests pass")
cypress/directory in the root of the project